Print

March 25, 2009

Sitecore CMS V5.3.2 rev. 090317 is released.

You should only use Sitecore 5.3.2 rev. 090317 if you are affected by one of the issues fixed by this release.

Change log:

Issues resolved:

• Fixed: Sitecore would sometimes add a "db=master" attribute to the source of image fields after editing the image properties. As a result image was always retrieved from the master database.

• Fixed: Sitecore’s caches could become corrupted under heavy load. This resulted in occasional “Item not found”, “Layout not found”, “Device not found” or “Rendering item not found” messages appearing in Sitecore log files or a public web site.

• Fixed: The Installation Wizard would never install files that were marked with "skip if exists".

• Fixed: When using dynamic image scaling, the right and bottom edge of the image would sometimes appear cropped.

• Fixed: Sitecore would throw an error when uploading a file that had a name which was similar to a GUID.

• Fixed: If user did not have access to some of the selected values of a lookup field and saved the item, the field would lose these selected values. This applies to the following field types: Lookup, ValueLookup, Multilist, Checklist.

• Fixed: The MaxItemNameLength setting from web.config was never taken into account. Users were never allowed to create an item with more than 100 characters in the item name.

February 20, 2009

Sitecore CMS V5.3.2 rev. 090212 is released.    This is the current Recommended Release.

Change log:

Issues resolved:

• Fixed: By default, the Sitecore web service is now restricted so only Administrators and members of the Sitecore Client Securing role can retrieve data from security databases using the web service. To allow any user to retrieve data from one or more security databases using the web service, specify a pipe-separated list of security database names in the WebService.IgnoreSecurityRestriction setting in the web.config (ex. "security|extranet").
   
  Credit
  Sitecore Corp. wants to give credit to the National Australia Bank Security Assurance Team for the discovery of this vulnerability and for their cooperation.

October 22, 2008

Sitecore CMS V5.3.2 rev. 081002 is released.

You should only use Sitecore 5.3.2 if you are affected by one of the issues fixed by this release.

Change log:

Issues resolved:

• Fixed: Sitecore would display an error message if a user tried to copy an item with virtual subitem.

• Fixed: When deleting a virtual item, existing links to the real item were not always updated, no matter if the user selected “Remove Links” or “Link to Another Item” in the “Broken Link” dialog.

• Fixed: The Media cache could grow much larger than expected due to caching the same images multiple times.

• Fixed: The Treelist field type did not work correctly in Firefox.

• Fixed: Changes made in the Rich Text editor were not visible when switching to the HTML view when using Firefox.

• Fixed: It was not possible to switch back from HTML view to Design view when using Firefox. 

June 05, 2008

Sitecore CMS V5.3.2 rev. 080521 is released.

You should only use Sitecore 5.3.2 if you are affected by one of the issues fixed by this release.

Change log:

Issues resolved:

• Fixed: Sitecore sometimes threw an error if users logged in simultaneously in several threads.

• Fixed: Field values may not have been published after having been reset to their __Standard Values.

• Fixed: When an item is deleted that is referenced by other items, the “Breaking Link” dialog offers a “remove links” option. If this option was chosen, Sitecore may have removed links to other items if they were stored in the same field but in other numbered or language versions of the item.

• Fixed: When rendering XSLTs in xml-output-mode (used to produce valid XHTML) some tags were collapsed if they did not have any content (for example <DIV></DIV> may have been collapsed to <DIV/>). This caused rendering errors in browsers which do not support collapsed tags.

April 08, 2008

Sitecore CMS V5.3.2 rev. 080324 is released. 

You should only use Sitecore 5.3.2 if you are affected by one of the issues fixed by this release.

Change log:

Issues resolved:

• Fixed: the deletion of a language from the core database caused the deletion of this language from the master database instead.

• Fixed: the Rich Text Editor could make unexpected changes to the html.

• Fixed: a conflict occurred if a Proxy and an Original items inherited different security from their parents.

• Fixed: an exception occurred if a semi-colon (;) was included in the Send To field of a reminder.

• Fixed: an item was always published with its subitems even if “Publish with subitems” toggle was unchecked.

• Fixed: changes in the Base Templates dialog were not saved.

• Fixed: the performance of Multilist/Lookup fields is improved in this release.

• Fixed: virtual items were displayed in the Preview Client even if the “Never Publish” checkbox was checked for the proxy items.

• Fixed: The Save button was disabled on the template fields and sections for the Sitecore Client Maintaining role.

January 09, 2008

Sitecore CMS V5.3.2 rev. 071220 is released. 

Sitecore 5.3.2 qualifies as a level 3 upgrade because this release introduces changes to the rendering engine required to solve an early data-binding issue with some unique .NET controls.  Although unlikely, this change could possibly influence other aspects of an upgraded site.

Resolved Issues:

• The Sitecore license check is now asynchronous, which improves performance.
• After item was saved the Renderings field was changed automatically. Therefore this field wasn’t inherited from the __Standard Values and didn't reflect changes the Renderings field was changed in the __Standard Values.
• If media item had an Updated\ Created time that was in the future an exception occurred in the Blob field of media item “Specified argument was out of the range of valid values. Parameter name: utcDate”.
• For each placeholder nesting level, init event of controls at a ‘deeper’ level fired after the load event of an ‘upper-level’ control.
• Sitecore CMS may stop writing to the log files after the ASP.NET restart. This was fixed in the following way: the Sitecore creates a new log file with “log.{date}.{time}.txt” name if it cannot access to the current log file. It is possible to always have time in the log file name by specifying {time} macro for the log files names in the web.config.
• The Indexing Manager can be disabled by specifying Indexing.UpdateInterval = 00:00:00 in the web.config file.
• Firefox showed incorrect filenames when downloading media files with spaces in their name.
• The Fallback device was not requested and “no layout defined” appeared if custom device was detected via a query string and a layout didn’t exist for the requested item.
• Items created via a Master were created in the Sitecore Client language instead of the language selected on the Language chunk.
• Search didn’t work if an extra index was specified in the web.config file with any fields. Now it is possible to specify an extra index in the web.config file: <index id=”_extra_index_” …> </index> and add any fields to be searchable there: <field …>_field_name_</field>.
• Export of custom language may work incorrectly. Some field values were not exported into XML file.
• Login to the Sitecore or Extranet domains took too long time after ~20000 users were added.
• If item had versions in several languages and a version in one of the languages was hidden, after publishing in the hidden language, the value of the shared field was cleared.
• Uploading of media with non-Unicode characters in the names was not possible.
• After the Shared checkbox was unchecked for a field, its value couldn’t be changed.
• The Upload.SimpleUploadOverwriting setting has been added to the web.config file. It may be set to false to not overwrite a media item when performing simple upload.
• Caching of proxy definitions in databases has been implemented.
• The Caching.AverageItemSize setting has been added to the web.config file.